home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SPACE 2
/
SPACE - Library 2 - Volume 1.iso
/
utility
/
634
/
read_me.1st
< prev
Wrap
Text File
|
1992-09-01
|
12KB
|
207 lines
ReadME.TXT
This is the first FreWare release of PowerDOS!
This file MUST be included with the PowerDOS.PRG.
(C)1992 DragonWare Software Inc. and (C)1992 PowerPoint Software.
ALL RIGHTS RESERVED!
Place the PowerDOS.PRG in the AUTO folder.
PowerDOS.PRG must be THE FIRST application run in the AUTO folder!
Place The POWERDOS folder in the Root directory of the same drive.
PowerDos is a very powerfull and compatible GEMDOS replacement.
Using PinHead:
You can place PinHead in the AUTO folder before PowerDOS. This will
speed up booting PowerDOS itself, but after PowerDOS is loaded,
PinHead will become dormant. PowerDOS itself incorporates some of the
same fast loading techniques as PinHead, and can be controlled with a
variable in the CONFIGUR file in the \POWERDOS folder on the boot
drive. See the variable descriptions below for further information.
FatSpeed, FolderXXX and other such fixes:
These are not needed, nor will they work with PowerDOS. Nor does
PowerDOS need them. The PowerDOS disk file system is much faster at
dealing with disks than GemDOS with FatSpeed. And as far as problems
with folder space allocation, this is a non-problem with PowerDOS as
it uses self expanding data structures for virtually everything. As
long as there is memory in the computer, PowerDOS will be able to open
another folder, or another file.
Below is a sample CONFIGUR file with descriptions of the variables
that may be set, how to set up default environment variables, and how
to execute TTP programs during bootup. Warning: this information may
be difficult to understand. This is why we made PDEXPERT.PRG
Note:
The CONFIGUR FILE that comes with PowerDOS is designed to work with
PDEXPERT. Do not add/Change the lines or data to the first 21 lines.
********** PowerDOS Configuration Variables **********
Note: Configuration variables must start on column one of the line.
By placing an asterisk in column one (or a space, or anything),
the variable is disabled, and the default will be used instead.
ticks=50 Ticks per second, gives length of a process timeslice.
Can be 200, 100, 50, 25 or 12. Default=50.
priority=128 Initial system priority. All processes inherit their
parents priority. Lower numbers give lower priority,
higher numbers give higher priority. Has little effect
unless many processes are running. Default=128
memrsv=50 Memory to reserve at top of ram. This is used to keep
memory hog programs from grabbing every available byte.
The network requires small blocks of ram to be avail-
able at all times. The next variable controls the size
of blocks allocated within the reserve area. Size given
as *1024 (50=51,200 bytes). Default=0, no reserve.
maxblrsv=5 Max size of blocks of ram that can be allocated within
the reserved area. This insures that network server
processes (which require < 5k each) can have enough
memory to run in when all other memory is used by hogs.
Size given as *1024 (5=5120 bytes). Default=0.
*maxtpa=4000 Maximum TPA size given to a program. When a program
is run, it is normally given all of memory to run in.
This memory is divided into text+data+bss+heap, with
the first three strictly defined by the program, the
fourth (heap) being all the rest of memory. The program
is supposed to free what it doesn't need of the heap,
but many don't, tying up all of memory. This variable
can be used to control the total memory given to a
program at startup. Size *1024. Default is no limit.
*maxmalloc=4000 Maximum memory returned for process Malloc(-1) call.
When most processes try to allocate more memory, they
will do a Malloc(-1) system call, which returns the
size of the largest block of memory. If there was a
3 megabyte block of memory available, the call would
return 3,000,000 and many programs would allocate the
whole thing, thus running the system out of memory
again. This variable sets a limit on what the OS
returns as a result. If this was set to 2000, and
there were 3 megs of memory in the system, the result
of the Malloc(-1) call would be 2,000,000. Size *1024.
Default is no limit.
*numdrives=26 Number of drive descriptors created. GemDOS will only
recognize 16 drives, A through P, without the MetaDOS
extension loaded. PowerDOS has no limit on the drives
it can access. It only requires a device descriptor to
be created for each drive. This variable lets you set
the number of drives from 1 to 26 (setting it to 1
would allow only drive A to be recognized). Note that
you would still need a BIOS driver that recognized
drives beyond P. Default is 16.
*fastload=32 Number of k of heap to clear on progam load. This is
similar to the popular public domain program 'PinHead'
by Charles F. Johnson. It controls the amount of memory
to clear when a program runs. If not used (default),
PowerDOS will clear all of the program's heap, unless
the fastload bit is set in the programs header, in
which case only 32k will be cleared. If a value is
given, then that much heap will be cleared for all
programs, and the fastload bit will be ignored.
*cache=256 Number of disk cache sectors to create. A disk cache
will greatly increase the speed of a hard drive by
storing commonly used sectors in ram. This cache is
built into the PowerDOS disk file system, and testing
shows it to be the fastest write through cache for
the ST (a write cache, like that built into ICD
software, is faster for many operations involving
writes). Legal values are 50-999. Less than 50 results
in a 50 sector cache. Default is no cache.
*auto=0 Used to control how PowerDOS handles the AUTO folder
on bootup. Since PowerDOS is run from the AUTO
folder itself, and replaces GemDOS, which was running
AUTO folder programs, PowerDOS must restart the AUTO
process itself. After it initializes itself, it runs
programs listed in this file. It then searches the AUTO
folder for programs, skipping all of them until it
finds the name 'POWERDOS.PRG'. It then runs any .PRG it
finds after that. This variable alows you to control
this process. If this is set to 'n', then no AUTO
programs will be run. If it is set to a number, then
that many AUTO programs will be skipped. Setting it
to zero means that it will run all AUTO programs.
Default is to look for 'POWERDOS.PRG'.
*autodrv=c Drive to continue auto folder operations from. The
network makes it possible to have a machine with only
a floppy disk boot with direct access to hard drives.
It is possible, therefore, that by the time PowerDOS
restarts the AUTO folder process, that there is a
drive C. Normally, however, PowerDOS would look for the
AUTO folder on whatever drive it was booted from. This
variable allows you to force PowerDOS to look in a
different drive for the AUTO forlder. It could even
be used to force bootup to continue on another drive
completely, like D or E (many programs might fail,
though, as they expact to run form A or C). Default
is whatever drive PowerDOS boots from.
*biosforce=y Force the use of standard handles from the BIOS. One
of the things a network provides is the ability to use
the devices of another machine over the network, like
a printer. The easiest way to do this is to redirect
standard handle number 3 (PRN) to the printer desired.
Any printer output using the function call Cprnout will
then go to the printer over the network. However, some
programs call the BIOS directly for printer support,
and so could not be redirected. This variable, when set
to 'y', will cause these BIOS calls to be re-issued as
regular DOS calls, where redirection can be performed.
Legal values are 'y'(es) or 'n'(o). Default is 'n'.
*negforce=y GemDOS provides the ability to bypass redirection of
the standard handles by using a negative number. If
a program used -3 for a handle, then output would
go to the PRN device, regardless of whether handle
3 had been redirected. GFA Basic is one source of
programs that do this. This would prevent redirection
just like using the BIOS directly. This variable, when
set to 'y', will force these negative handles to act
like the regular handles and perform redirection.
Default is 'n'.
********** Environment Variables **********
Environment variables may be set from this file using 'env=' followed
by typical 'variable=value' definitions. The 'env=' must start in the
first column, as with the other variables. Example:
env=PATH=C:\;\AUTO\;D:\DEVPAC
env=SUFF=.prg,.app,.tos,.ttp
Any number of environment variables may be defined. Note, anything after
the 'env=' up to the carriage return at the end of the line is considered
part of the variable, hence no comment may appear on the same line. If the
variable is too long for the line, it may be continued by including the
symbol '~' at the end of the line (right before the carriage return). The
next 'env=' statement will then be added on. Example:
env=PATH=C:\;\AUTO\;\CPX\;\ACCS\;\MODEM\;D:\;\DEVPAC\;\WWRITER\;\RCS\;~
env=\GAMES\;\DTP\;\PAINT\
********** How to Execute Programs **********
To have PowerDOS execute a program (before it resumes executing AUTO
folder programs), simply place the name of the program (the entire path
name if it does not reside in the POWERDOS folder) on a line by itself,
at the end of the file with a '#' sign in the first column. If the program
requires a command line, then put a single space at the end of the filename,
then a '$' then the command line. Example:
#aliasdrv.ttp $c,n:\node1\c\